Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45b33b02e8edf0fe8371f951434d56fd4cfbde06211dd7f3dc590100098845c7

Tx prefix hash: 0fc86d98636aae421290807f5341d93bc5fce57c9a90ef963a8b1bcc8d0bb317
Tx public key: a0dbb3eea9fa6a5ff90940338f352f3925aa12054c5354e117f6b26a7a139b31
Timestamp: 1737898906 Timestamp [UCT]: 2025-01-26 13:41:46 Age [y:d:h:m:s]: 00:330:11:57:29
Block: 1205748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233795 RingCT/type: yes/0
Extra: 01a0dbb3eea9fa6a5ff90940338f352f3925aa12054c5354e117f6b26a7a139b3102110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f677405b4d7320e53599b933353960972b4b9503909d4405773d1932850051d4 0.600000000000 1692447 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": 1205758, "vin": [ { "gen": { "height": 1205748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f677405b4d7320e53599b933353960972b4b9503909d4405773d1932850051d4" } } ], "extra": [ 1, 160, 219, 179, 238, 169, 250, 106, 95, 249, 9, 64, 51, 143, 53, 47, 57, 37, 170, 18, 5, 76, 83, 84, 225, 23, 246, 178, 106, 122, 19, 155, 49, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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