Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39418dd9fa564dc88c6463a7fa70dd40d204187ecf55aeb15569a31f6549525c

Tx prefix hash: 1e704de1906c86d7d6352d2f5662214e5da7ac18a1390d7c6db5dbad130f4a7f
Tx public key: 0c192122518cc92a655dbd73e2fd31c1bf68f1e3f34ab0a08855df06c329df2d
Timestamp: 1726600382 Timestamp [UCT]: 2024-09-17 19:13:02 Age [y:d:h:m:s]: 00:209:08:21:12
Block: 1112270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149461 RingCT/type: yes/0
Extra: 010c192122518cc92a655dbd73e2fd31c1bf68f1e3f34ab0a08855df06c329df2d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a568f394a8d488840b414d7a47a70c59f7f2e555a88d6847bc8565a3723be5ef 0.600000000000 1591533 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": 1112280, "vin": [ { "gen": { "height": 1112270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a568f394a8d488840b414d7a47a70c59f7f2e555a88d6847bc8565a3723be5ef" } } ], "extra": [ 1, 12, 25, 33, 34, 81, 140, 201, 42, 101, 93, 189, 115, 226, 253, 49, 193, 191, 104, 241, 227, 243, 74, 176, 160, 136, 85, 223, 6, 195, 41, 223, 45, 2, 17, 0, 0, 0, 4, 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