Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13d5f2f0ef6db91c3eb15eeb3e89dff277a1943d9c9848b65540263c16171560

Tx prefix hash: 358aa37bb1917642e969b5dc606c9f6ee7c017a80cd8c512050699d432d3f56a
Tx public key: cf1eb4927ddc7593f97286902765a692f78a034b5110123218c8fdae79046540
Timestamp: 1741970649 Timestamp [UTC]: 2025-03-14 16:44:09 Age [y:d:h:m:s]: 01:252:20:15:47
Block: 1239248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444246 RingCT/type: yes/0
Extra: 01cf1eb4927ddc7593f97286902765a692f78a034b5110123218c8fdae790465400211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ef14adc82b0649db52e3ce43f3f575f74d11fd221c84d49630287dd849e1658 0.000600000000 1726213 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": 1239258, "vin": [ { "gen": { "height": 1239248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ef14adc82b0649db52e3ce43f3f575f74d11fd221c84d49630287dd849e1658" } } ], "extra": [ 1, 207, 30, 180, 146, 125, 220, 117, 147, 249, 114, 134, 144, 39, 101, 166, 146, 247, 138, 3, 75, 81, 16, 18, 50, 24, 200, 253, 174, 121, 4, 101, 64, 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: