Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d732f448c1e612ca87da9434c15b668db67206d7b69d07c73ab2557b2deff77

Tx prefix hash: ac008e2dc7adb3fb8433f7fdb7ea53374dfa7f58556bfa909ac1c696b3e08278
Tx public key: 810acb1231a44ab55a6b5ce5b8d50df40ce5a10d58d8fed7148735cb1576ab10
Timestamp: 1745974652 Timestamp [UCT]: 2025-04-30 00:57:32 Age [y:d:h:m:s]: 00:008:03:22:29
Block: 1272385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5812 RingCT/type: yes/0
Extra: 01810acb1231a44ab55a6b5ce5b8d50df40ce5a10d58d8fed7148735cb1576ab1002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c83e7dbb657ac42763f5d6e8c862b34bae591b2e15f90a260b6a6985c62db873 0.600000000000 1759660 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": 1272395, "vin": [ { "gen": { "height": 1272385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c83e7dbb657ac42763f5d6e8c862b34bae591b2e15f90a260b6a6985c62db873" } } ], "extra": [ 1, 129, 10, 203, 18, 49, 164, 74, 181, 90, 107, 92, 229, 184, 213, 13, 244, 12, 229, 161, 13, 88, 216, 254, 215, 20, 135, 53, 203, 21, 118, 171, 16, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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