Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58a484f4c298c2cad3edb2b3045f259ac27488ed2176705c3ace067e5c2b31d4

Tx prefix hash: 0a349799f197e32f3c6fc684b619e639928545baa787c2900f40f817b6f867f5
Tx public key: e00ab4f9ddd9c954e9a251897b5e4cd978c6d4b8ee1f2e10cd1ca7712286d74e
Timestamp: 1755876527 Timestamp [UCT]: 2025-08-22 15:28:47 Age [y:d:h:m:s]: 00:043:09:12:39
Block: 1352061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30888 RingCT/type: yes/0
Extra: 01e00ab4f9ddd9c954e9a251897b5e4cd978c6d4b8ee1f2e10cd1ca7712286d74e021100000016b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7dd956141d628f02ff1e666ab7d035c939aa4a324eacde5ceb523d5ede642d8 0.600000000000 1840022 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": 1352071, "vin": [ { "gen": { "height": 1352061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7dd956141d628f02ff1e666ab7d035c939aa4a324eacde5ceb523d5ede642d8" } } ], "extra": [ 1, 224, 10, 180, 249, 221, 217, 201, 84, 233, 162, 81, 137, 123, 94, 76, 217, 120, 198, 212, 184, 238, 31, 46, 16, 205, 28, 167, 113, 34, 134, 215, 78, 2, 17, 0, 0, 0, 22, 178, 247, 132, 196, 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