Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72d0353d610fd6fcfdd622399e143d20ea93f6814b6a35b0749653ff5fb321d6

Tx prefix hash: cd68e7aa718d4d88f11731de2031f2fa807fc0ede513e1209a782cca23254dbb
Tx public key: 2d4b045f750a7074e00d399cd32f17e90869318b7ded770263608a943244db3e
Timestamp: 1740419548 Timestamp [UTC]: 2025-02-24 17:52:28 Age [y:d:h:m:s]: 01:084:02:00:53
Block: 1226373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312107 RingCT/type: yes/0
Extra: 012d4b045f750a7074e00d399cd32f17e90869318b7ded770263608a943244db3e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d0b4318f4ce08c7ff14056b0ad213cd3f5cc974cdfd4409fb390552b39d53e09 0.000600000000 1713244 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": 1226383, "vin": [ { "gen": { "height": 1226373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0b4318f4ce08c7ff14056b0ad213cd3f5cc974cdfd4409fb390552b39d53e09" } } ], "extra": [ 1, 45, 75, 4, 95, 117, 10, 112, 116, 224, 13, 57, 156, 211, 47, 23, 233, 8, 105, 49, 139, 125, 237, 119, 2, 99, 96, 138, 148, 50, 68, 219, 62, 2, 17, 0, 0, 0, 1, 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) | monero version: