Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 041859ef9417e1d8f63c77825fefb321b3eb4ce7415a5df161be9afa2b5bdb33

Tx prefix hash: 2fb48fa38d7faad126710c8b117ed55a9f1a087793bd40dfa577b90232ba03f4
Tx public key: 8e4b18e5f32daca93ac7f20b4a5307b8922e8593e25883388d525e728afcb7fe
Timestamp: 1749700504 Timestamp [UCT]: 2025-06-12 03:55:04 Age [y:d:h:m:s]: 00:153:05:20:09
Block: 1303200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107210 RingCT/type: yes/0
Extra: 018e4b18e5f32daca93ac7f20b4a5307b8922e8593e25883388d525e728afcb7fe021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb513b216c85344a8fc33dca297d081a40d50a1ce15128df9818549e70a16979 0.600000000000 1790777 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": 1303210, "vin": [ { "gen": { "height": 1303200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb513b216c85344a8fc33dca297d081a40d50a1ce15128df9818549e70a16979" } } ], "extra": [ 1, 142, 75, 24, 229, 243, 45, 172, 169, 58, 199, 242, 11, 74, 83, 7, 184, 146, 46, 133, 147, 226, 88, 131, 56, 141, 82, 94, 114, 138, 252, 183, 254, 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