Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f3d5900bfe18db2ed0ce0c66367224024ab9d0bc40b44e3fbdbdfb76af10a1

Tx prefix hash: 5628bdb1881c98fba199a1e4bf3c6276c9a80ece40d9bf624edd889a93814ab6
Tx public key: cae2e619ce548f754e14b851b83d83c5cab82b3505e006d6797927db2d9c9483
Timestamp: 1672600911 Timestamp [UCT]: 2023-01-01 19:21:51 Age [y:d:h:m:s]: 02:015:11:29:48
Block: 665456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532970 RingCT/type: yes/0
Extra: 01cae2e619ce548f754e14b851b83d83c5cab82b3505e006d6797927db2d9c948302110000000375e3f0e9000000000000000000

1 output(s) for total of 3.828846820000 dcy

stealth address amount amount idx
00: 5e21d8be433737f2efa7aee503f385e9dd1b996923a774e2c3b201605e555717 3.828846820000 1106499 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": 665466, "vin": [ { "gen": { "height": 665456 } } ], "vout": [ { "amount": 3828846820, "target": { "key": "5e21d8be433737f2efa7aee503f385e9dd1b996923a774e2c3b201605e555717" } } ], "extra": [ 1, 202, 226, 230, 25, 206, 84, 143, 117, 78, 20, 184, 81, 184, 61, 131, 197, 202, 184, 43, 53, 5, 224, 6, 214, 121, 121, 39, 219, 45, 156, 148, 131, 2, 17, 0, 0, 0, 3, 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