Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27e79c01e894df1dc1f459d50873fd8cb19d49e67d556de7341ac90ab08881f7

Tx prefix hash: f0145a1a2aea53157d5c8e59a16915465ce872423451ab00180d5f6084df0719
Tx public key: a8d4485f14b392500d0194e2b3415fed161ff67e6d4a94b49b37bff83e78c93d
Timestamp: 1710178969 Timestamp [UCT]: 2024-03-11 17:42:49 Age [y:d:h:m:s]: 01:074:04:47:41
Block: 976150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314046 RingCT/type: yes/0
Extra: 01a8d4485f14b392500d0194e2b3415fed161ff67e6d4a94b49b37bff83e78c93d02110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b23bc75e2ab753926b424177501f54306c5cec6d6b74d2278e5ed4584cc3b6cf 0.600000000000 1436139 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": 976160, "vin": [ { "gen": { "height": 976150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b23bc75e2ab753926b424177501f54306c5cec6d6b74d2278e5ed4584cc3b6cf" } } ], "extra": [ 1, 168, 212, 72, 95, 20, 179, 146, 80, 13, 1, 148, 226, 179, 65, 95, 237, 22, 31, 246, 126, 109, 74, 148, 180, 155, 55, 191, 248, 62, 120, 201, 61, 2, 17, 0, 0, 0, 16, 82, 212, 126, 148, 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