Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 978ebcece0cc164bfdb4cb54bbd6b3455c32f9b412340b164fab6d402562b062

Tx prefix hash: 9975a23e1a71211ee027e18a63a2a7a68c344115ca3928428af82151eb177f84
Tx public key: c695caa1cc116f66f8084d7865dcfce3a882172ef1069d3120bafcb4563e77f0
Timestamp: 1674194890 Timestamp [UTC]: 2023-01-20 06:08:10 Age [y:d:h:m:s]: 03:304:08:31:51
Block: 678672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1003280 RingCT/type: yes/0
Extra: 01c695caa1cc116f66f8084d7865dcfce3a882172ef1069d3120bafcb4563e77f00211000000025029cbac000000000000000000

1 output(s) for total of 0.003461607940 xmr

stealth address amount amount idx tag
00: f383305c53caf9dbbf510a34e75f3662e9721fff3330e5dfd81c4279c9d5a65b 0.003461607940 1120563 of 0 -

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": 678682, "vin": [ { "gen": { "height": 678672 } } ], "vout": [ { "amount": 3461607940, "target": { "key": "f383305c53caf9dbbf510a34e75f3662e9721fff3330e5dfd81c4279c9d5a65b" } } ], "extra": [ 1, 198, 149, 202, 161, 204, 17, 111, 102, 248, 8, 77, 120, 101, 220, 252, 227, 168, 130, 23, 46, 241, 6, 157, 49, 32, 186, 252, 180, 86, 62, 119, 240, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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) | monero version: