Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5028b6f84ccc8ab4c05a816773b88e73c552222225249f4cb3c6bd103a7bc3cb

Tx prefix hash: 22916939f01834d28eb8bac1e7fc6524c71808534c3075a98afd3a12285d8ca8
Tx public key: 472acaf2a6f9a087f6ee8fc9f88a93d781eadd7501b3d147556ee225c545543f
Timestamp: 1707803536 Timestamp [UCT]: 2024-02-13 05:52:16 Age [y:d:h:m:s]: 01:125:12:41:34
Block: 956433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350684 RingCT/type: yes/0
Extra: 01472acaf2a6f9a087f6ee8fc9f88a93d781eadd7501b3d147556ee225c545543f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a09ccae7854a9cb8baec6f3582a9c0e2b9381fe20d1096cd9a8b42705755d65 0.600000000000 1415741 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": 956443, "vin": [ { "gen": { "height": 956433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a09ccae7854a9cb8baec6f3582a9c0e2b9381fe20d1096cd9a8b42705755d65" } } ], "extra": [ 1, 71, 42, 202, 242, 166, 249, 160, 135, 246, 238, 143, 201, 248, 138, 147, 215, 129, 234, 221, 117, 1, 179, 209, 71, 85, 110, 226, 37, 197, 69, 84, 63, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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