Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f3cb0077e28f8de69c3528832bc7cd0e0c35d2860176d8d831c0b5b414e4bc9

Tx prefix hash: ca4d31848879b25f3c1f8d490afdd5cd098ae320d6cd3917a2ea8bdcfdea729b
Tx public key: 369512d6df1f0000d5761c1c98185b5abefe66c8a40ef7ae09bb49a0abb6342e
Timestamp: 1773785497 Timestamp [UTC]: 2026-03-17 22:11:37 Age [y:d:h:m:s]: 00:241:14:21:18
Block: 1500058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178077 RingCT/type: yes/0
Extra: 01369512d6df1f0000d5761c1c98185b5abefe66c8a40ef7ae09bb49a0abb6342e021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ad655cece7f1e19d4663b216d1425c1c2bf9d4f83e8be9c8c757e9040989f512 0.000600000000 1989726 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": 1500068, "vin": [ { "gen": { "height": 1500058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad655cece7f1e19d4663b216d1425c1c2bf9d4f83e8be9c8c757e9040989f512" } } ], "extra": [ 1, 54, 149, 18, 214, 223, 31, 0, 0, 213, 118, 28, 28, 152, 24, 91, 90, 190, 254, 102, 200, 164, 14, 247, 174, 9, 187, 73, 160, 171, 182, 52, 46, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: