Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f54abe132002ed1411723940955aeacbe2d1c24e765a9539c41f5e8b50de5aa

Tx prefix hash: 6dee1e252d3ec9710ca3939ea03292a66c511e0685976293aaa3866f953cbf91
Tx public key: 2d67a1edb7a2f662f4698b89304fb6018ca96c1cf9f4a7ce0b59c075e17c37e1
Timestamp: 1727205518 Timestamp [UCT]: 2024-09-24 19:18:38 Age [y:d:h:m:s]: 00:197:02:44:04
Block: 1117293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140689 RingCT/type: yes/0
Extra: 012d67a1edb7a2f662f4698b89304fb6018ca96c1cf9f4a7ce0b59c075e17c37e1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae650a21fab9d0e8bfaf138f036590dffd151517fadcfe2bbc6da93cc499a8ec 0.600000000000 1598078 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": 1117303, "vin": [ { "gen": { "height": 1117293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae650a21fab9d0e8bfaf138f036590dffd151517fadcfe2bbc6da93cc499a8ec" } } ], "extra": [ 1, 45, 103, 161, 237, 183, 162, 246, 98, 244, 105, 139, 137, 48, 79, 182, 1, 140, 169, 108, 28, 249, 244, 167, 206, 11, 89, 192, 117, 225, 124, 55, 225, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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