Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 805077b2b8d33a45ed47eacf5caa559f5b8651f980d09d702356ffab013a800a

Tx prefix hash: 7332764a7d58742a0bbdf918803c174d3675e2128e8c33d4b79d5dc78c59ca1c
Tx public key: 6fb0037de44bb7cb5fd275f944b289e9f2ae73d8f5e07ad6a554e5423cfde436
Timestamp: 1724604640 Timestamp [UCT]: 2024-08-25 16:50:40 Age [y:d:h:m:s]: 00:136:15:56:54
Block: 1095734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97754 RingCT/type: yes/0
Extra: 016fb0037de44bb7cb5fd275f944b289e9f2ae73d8f5e07ad6a554e5423cfde43602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435087c1b7a945ebd24edeb5533597662b7dfa36590e68d1d7248163b4267b05 0.600000000000 1570915 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1095744, "vin": [ { "gen": { "height": 1095734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435087c1b7a945ebd24edeb5533597662b7dfa36590e68d1d7248163b4267b05" } } ], "extra": [ 1, 111, 176, 3, 125, 228, 75, 183, 203, 95, 210, 117, 249, 68, 178, 137, 233, 242, 174, 115, 216, 245, 224, 122, 214, 165, 84, 229, 66, 60, 253, 228, 54, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8