Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb3afddc4d8fef3ba23daa268b4c90ffd489e1c07eaed785931fa390ddc56d3

Tx prefix hash: 254e6eb47bc5c178c68bb60feab38ba74a54b105170c0b3f2a47d6572fba92fb
Tx public key: 04df4d3e1d00489824e5ec9bf02b62614f08b06c01af769405120deace684f78
Timestamp: 1741765118 Timestamp [UTC]: 2025-03-12 07:38:38 Age [y:d:h:m:s]: 00:341:12:42:10
Block: 1237540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241740 RingCT/type: yes/0
Extra: 0104df4d3e1d00489824e5ec9bf02b62614f08b06c01af769405120deace684f780211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f7ad7dc70107755088cf4be72fa49819ac1c371a2384a13f5c54226cb10c6a9 0.000600000000 1724495 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 dinastycoin-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": 1237550, "vin": [ { "gen": { "height": 1237540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f7ad7dc70107755088cf4be72fa49819ac1c371a2384a13f5c54226cb10c6a9" } } ], "extra": [ 1, 4, 223, 77, 62, 29, 0, 72, 152, 36, 229, 236, 155, 240, 43, 98, 97, 79, 8, 176, 108, 1, 175, 118, 148, 5, 18, 13, 234, 206, 104, 79, 120, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369