Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de40e52b43d5561f5d20059ba24742c31e676f8451fdb43b2638073d63b6ed0

Tx prefix hash: 25cb5626d0d25e72198276d6c9d9d4d5b04d1c44251dae0c7c182b907c132734
Tx public key: e8a36507eff8568e07f289869eefb5c60975a82016aa737bf2c079fc5c952cdb
Timestamp: 1647937824 Timestamp [UCT]: 2022-03-22 08:30:24 Age [y:d:h:m:s]: 02:280:00:39:57
Block: 463832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719656 RingCT/type: yes/0
Extra: 01e8a36507eff8568e07f289869eefb5c60975a82016aa737bf2c079fc5c952cdb021100000001bf7ee4e7000000000000000000

1 output(s) for total of 17.832178062000 dcy

stealth address amount amount idx
00: bc50c524e60a6b0b1a1145b6d8f44ab720cc3a559106ad955ab3f5ddce6303fa 17.832178062000 881575 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": 463842, "vin": [ { "gen": { "height": 463832 } } ], "vout": [ { "amount": 17832178062, "target": { "key": "bc50c524e60a6b0b1a1145b6d8f44ab720cc3a559106ad955ab3f5ddce6303fa" } } ], "extra": [ 1, 232, 163, 101, 7, 239, 248, 86, 142, 7, 242, 137, 134, 158, 239, 181, 198, 9, 117, 168, 32, 22, 170, 115, 123, 242, 192, 121, 252, 92, 149, 44, 219, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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