Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5af2b44d348ca2129bd420235e48c3b85b9bf81dbe4e965a0ab3ede72faeb009

Tx prefix hash: b9c611837a2f574cd759dd0f937ee5c21077402be2311805e01a015287855bc8
Tx public key: 62faca1aa21451ffb4470917d8ed1f0b40b8b5f838b7832d7e5c63282c8b3b13
Timestamp: 1648626987 Timestamp [UCT]: 2022-03-30 07:56:27 Age [y:d:h:m:s]: 03:219:19:12:48
Block: 469440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935069 RingCT/type: yes/0
Extra: 0162faca1aa21451ffb4470917d8ed1f0b40b8b5f838b7832d7e5c63282c8b3b1302110000000e37cb3088000000000000000000

1 output(s) for total of 17.082469598000 dcy

stealth address amount amount idx
00: 4bf03dbe039249b57977706c3439bb606e9fef5d7cfaf03ccafef9c87984e917 17.082469598000 888388 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": 469450, "vin": [ { "gen": { "height": 469440 } } ], "vout": [ { "amount": 17082469598, "target": { "key": "4bf03dbe039249b57977706c3439bb606e9fef5d7cfaf03ccafef9c87984e917" } } ], "extra": [ 1, 98, 250, 202, 26, 162, 20, 81, 255, 180, 71, 9, 23, 216, 237, 31, 11, 64, 184, 181, 248, 56, 183, 131, 45, 126, 92, 99, 40, 44, 139, 59, 19, 2, 17, 0, 0, 0, 14, 55, 203, 48, 136, 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