Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c17f93465650fce36ec5a65892d2d4cc91432ae70e227bfc7a5113bdded451

Tx prefix hash: d71a86763e0e8cb084f242296c4c20116e216dff18ab4b5cfc321c99130ec73a
Tx public key: 81f90662400fc625cc3f3b7c646d1c6135a3ad05b58eecac209f1f8d224bfa4f
Timestamp: 1685060437 Timestamp [UCT]: 2023-05-26 00:20:37 Age [y:d:h:m:s]: 02:166:06:01:36
Block: 768140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638605 RingCT/type: yes/0
Extra: 0181f90662400fc625cc3f3b7c646d1c6135a3ad05b58eecac209f1f8d224bfa4f02110000000433af99f4000000000000000000

1 output(s) for total of 1.749175906000 dcy

stealth address amount amount idx
00: 8d0a09330b93b6ed2a4c130fc4afe6136391b36fc4ff61371c6ec15358982796 1.749175906000 1217327 of 0

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": 768150, "vin": [ { "gen": { "height": 768140 } } ], "vout": [ { "amount": 1749175906, "target": { "key": "8d0a09330b93b6ed2a4c130fc4afe6136391b36fc4ff61371c6ec15358982796" } } ], "extra": [ 1, 129, 249, 6, 98, 64, 15, 198, 37, 204, 63, 59, 124, 100, 109, 28, 97, 53, 163, 173, 5, 181, 142, 236, 172, 32, 159, 31, 141, 34, 75, 250, 79, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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