Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7d003aad05cf8d25f3ae10a40801032816c258f57b340838430f3199e0d5fb1

Tx prefix hash: dae1e6ecf84633f0c388ff9a7c97c43f52becf9f9661abff8bf5954fad9ebdd0
Tx public key: 88913ee9bf5051c64c443317c5e8450fcb468b9b4675413905e0801bc97a8b7c
Timestamp: 1720562307 Timestamp [UCT]: 2024-07-09 21:58:27 Age [y:d:h:m:s]: 00:271:03:02:51
Block: 1062222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193697 RingCT/type: yes/0
Extra: 0188913ee9bf5051c64c443317c5e8450fcb468b9b4675413905e0801bc97a8b7c02110000001691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fe51caadd1fdc3854a2d7f29e645d48ad4490f321cff29f5f2d8c8a1aa25e4b 0.600000000000 1532723 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": 1062232, "vin": [ { "gen": { "height": 1062222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fe51caadd1fdc3854a2d7f29e645d48ad4490f321cff29f5f2d8c8a1aa25e4b" } } ], "extra": [ 1, 136, 145, 62, 233, 191, 80, 81, 198, 76, 68, 51, 23, 197, 232, 69, 15, 203, 70, 139, 155, 70, 117, 65, 57, 5, 224, 128, 27, 201, 122, 139, 124, 2, 17, 0, 0, 0, 22, 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