Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b29b945f37b91e1dd423209c216c7e0ba7e407de942d88f61be2bed5b2db082

Tx prefix hash: cf0dfbe897737a7f963d15dffd39d8e67547abc1e37d69fa6aa0dcc7ee83de6b
Tx public key: 03cb02a09a033715b69d01ac44aba14fac153660999985e5bdb52c52c5c30079
Timestamp: 1741950057 Timestamp [UTC]: 2025-03-14 11:00:57 Age [y:d:h:m:s]: 01:250:16:10:31
Block: 1239078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443278 RingCT/type: yes/0
Extra: 0103cb02a09a033715b69d01ac44aba14fac153660999985e5bdb52c52c5c30079021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e1adc0d30fc02733bc421984ef2fbcb2dc79617e088a0e62416529f955b1d92 0.000600000000 1726043 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": 1239088, "vin": [ { "gen": { "height": 1239078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e1adc0d30fc02733bc421984ef2fbcb2dc79617e088a0e62416529f955b1d92" } } ], "extra": [ 1, 3, 203, 2, 160, 154, 3, 55, 21, 182, 157, 1, 172, 68, 171, 161, 79, 172, 21, 54, 96, 153, 153, 133, 229, 189, 181, 44, 82, 197, 195, 0, 121, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: