Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d6d5e64d673a77d0e543e04b3003acd85d28a7230038dbe79f75d66eaa004c

Tx prefix hash: 4d75fb25e86f829a1756f5b1c0c4d85cc75b43d75d400f8377d08b4d27bbaf98
Tx public key: 10347848629506d9d52cbec9807c81b2df5d93c2035675436448c53aa463f896
Timestamp: 1702455613 Timestamp [UCT]: 2023-12-13 08:20:13 Age [y:d:h:m:s]: 01:130:21:35:08
Block: 912124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354676 RingCT/type: yes/0
Extra: 0110347848629506d9d52cbec9807c81b2df5d93c2035675436448c53aa463f89602110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0636d9682a6a4a3110dcb4262e1792428383caefd2fa5a3abfcf3e1c4b3b15 0.600000000000 1369344 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": 912134, "vin": [ { "gen": { "height": 912124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0636d9682a6a4a3110dcb4262e1792428383caefd2fa5a3abfcf3e1c4b3b15" } } ], "extra": [ 1, 16, 52, 120, 72, 98, 149, 6, 217, 213, 44, 190, 201, 128, 124, 129, 178, 223, 93, 147, 194, 3, 86, 117, 67, 100, 72, 197, 58, 164, 99, 248, 150, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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