Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5d2eafa43b05b665129104ba22c0e69a6b137d8b55fc40d395511e3811c769

Tx prefix hash: 04e69476580a9eee1a19a78f0d30eca12821642ea06f13c0920092cd5149a47e
Tx public key: 93b3470afe4c302610cdbfd1294ed3bcbb5acaf1d2e41741f7214822bffa412f
Timestamp: 1735715110 Timestamp [UCT]: 2025-01-01 07:05:10 Age [y:d:h:m:s]: 00:306:21:33:34
Block: 1187708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216845 RingCT/type: yes/0
Extra: 0193b3470afe4c302610cdbfd1294ed3bcbb5acaf1d2e41741f7214822bffa412f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a05cf7995f1e5e39aa36ec5e0f5a133971c6a4d88aae9afcfa5d23706b3ef9c4 0.600000000000 1674201 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": 1187718, "vin": [ { "gen": { "height": 1187708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a05cf7995f1e5e39aa36ec5e0f5a133971c6a4d88aae9afcfa5d23706b3ef9c4" } } ], "extra": [ 1, 147, 179, 71, 10, 254, 76, 48, 38, 16, 205, 191, 209, 41, 78, 211, 188, 187, 90, 202, 241, 210, 228, 23, 65, 247, 33, 72, 34, 191, 250, 65, 47, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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