Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4e5d3121b272340e6cb860d7215ca5a3d66e0c8f52af9317c5a888fbc0d016

Tx prefix hash: dd205d0acb4c619d5c6885ddcdb9c5c99b5be7602027b86a5bfdc23fbfdcc3f6
Tx public key: 5aaae8d6e0b8e7a3950a201c8a8ed28e7a6235758cca6bc8b89242052cbc904d
Timestamp: 1722375467 Timestamp [UCT]: 2024-07-30 21:37:47 Age [y:d:h:m:s]: 00:249:11:20:28
Block: 1077246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178201 RingCT/type: yes/0
Extra: 015aaae8d6e0b8e7a3950a201c8a8ed28e7a6235758cca6bc8b89242052cbc904d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f7085bb63c1ec8b1ec75683ca4a3042104806030370b0d51bdd01b38e3a69b5 0.600000000000 1549793 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": 1077256, "vin": [ { "gen": { "height": 1077246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f7085bb63c1ec8b1ec75683ca4a3042104806030370b0d51bdd01b38e3a69b5" } } ], "extra": [ 1, 90, 170, 232, 214, 224, 184, 231, 163, 149, 10, 32, 28, 138, 142, 210, 142, 122, 98, 53, 117, 140, 202, 107, 200, 184, 146, 66, 5, 44, 188, 144, 77, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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