Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29c90eaca0b5f373edef44ee58a6e01ac8fee2df2db6cb2622383eb4fef52ad4

Tx prefix hash: be0fd13b9076c6555605806565006027cb4665d527daaf0fc9c1a387f0811558
Tx public key: a51b01c8475160f3f2956b34f6559e8902782a305d00e0d2a21edf3c5f581bcd
Timestamp: 1710616350 Timestamp [UCT]: 2024-03-16 19:12:30 Age [y:d:h:m:s]: 00:343:12:15:08
Block: 979774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245564 RingCT/type: yes/0
Extra: 01a51b01c8475160f3f2956b34f6559e8902782a305d00e0d2a21edf3c5f581bcd021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 110ddd46a412a39ec0bd586740290275e67be8cb07d95dbf2d502df09b0e2ee3 0.600000000000 1439827 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": 979784, "vin": [ { "gen": { "height": 979774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "110ddd46a412a39ec0bd586740290275e67be8cb07d95dbf2d502df09b0e2ee3" } } ], "extra": [ 1, 165, 27, 1, 200, 71, 81, 96, 243, 242, 149, 107, 52, 246, 85, 158, 137, 2, 120, 42, 48, 93, 0, 224, 210, 162, 30, 223, 60, 95, 88, 27, 205, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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