Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbc28acc3e87533bd5b548f8a42876fa919301290399e341b3dbf1ca9787d044

Tx prefix hash: a4a8bd3e5d03ec2f7df3ea044e38145f592bb0fd282816aeffce270f3af4968f
Tx public key: 8d7aa8f3154fe1bed5d8c15403b222d03ecbfe625f3b03916afc86714d447fe2
Timestamp: 1751060112 Timestamp [UCT]: 2025-06-27 21:35:12 Age [y:d:h:m:s]: 00:139:08:35:38
Block: 1314093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97663 RingCT/type: yes/0
Extra: 018d7aa8f3154fe1bed5d8c15403b222d03ecbfe625f3b03916afc86714d447fe2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd723396b273145cfffea393c0398e8508a7a573895b56466e987f0f086a0dc1 0.600000000000 1801738 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": 1314103, "vin": [ { "gen": { "height": 1314093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd723396b273145cfffea393c0398e8508a7a573895b56466e987f0f086a0dc1" } } ], "extra": [ 1, 141, 122, 168, 243, 21, 79, 225, 190, 213, 216, 193, 84, 3, 178, 34, 208, 62, 203, 254, 98, 95, 59, 3, 145, 106, 252, 134, 113, 77, 68, 127, 226, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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