Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d3b291d36115b094554a38f0050f20de9f1e79294b01bf2f4f16a8a8bd68019

Tx prefix hash: 3526cc53c00ce05763017fa84d1a56abb2a9f45b23773378ff8904e6bc0ebec0
Tx public key: b0b34a59e0facced5afe09cbf8a2ff2f16f168cd8c9be4440a49d064a8aa838e
Timestamp: 1743125013 Timestamp [UTC]: 2025-03-28 01:23:33 Age [y:d:h:m:s]: 01:239:13:47:53
Block: 1248782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434712 RingCT/type: yes/0
Extra: 01b0b34a59e0facced5afe09cbf8a2ff2f16f168cd8c9be4440a49d064a8aa838e021100000002d2e40efd000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: da38467e4b403e47fe574fbeb88f4e4d6c022bf42bbb5698c733f2c1173641f7 0.000600000000 1735817 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": 1248792, "vin": [ { "gen": { "height": 1248782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da38467e4b403e47fe574fbeb88f4e4d6c022bf42bbb5698c733f2c1173641f7" } } ], "extra": [ 1, 176, 179, 74, 89, 224, 250, 204, 237, 90, 254, 9, 203, 248, 162, 255, 47, 22, 241, 104, 205, 140, 155, 228, 68, 10, 73, 208, 100, 168, 170, 131, 142, 2, 17, 0, 0, 0, 2, 210, 228, 14, 253, 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: