Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf2738a2a63f73df55d0165194869f0b7bbeb3b62618da4136ef953824ff85e2

Tx prefix hash: e3fef2e9c7bb37d049e4356348d0dbb1f4f76239b766ca5230f244a7007dd24a
Tx public key: dd4cfabf7fc958db18fbe14dd595e9bf1530bdd4bb3a92694df0aa1167bb6e26
Timestamp: 1743059582 Timestamp [UTC]: 2025-03-27 07:13:02 Age [y:d:h:m:s]: 01:239:14:21:11
Block: 1248234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435260 RingCT/type: yes/0
Extra: 01dd4cfabf7fc958db18fbe14dd595e9bf1530bdd4bb3a92694df0aa1167bb6e260211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3f881f02dd5fc294e9c32ba8064805d4f28bc9775f6cad61dce73275eb4fc8cc 0.000600000000 1735263 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": 1248244, "vin": [ { "gen": { "height": 1248234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f881f02dd5fc294e9c32ba8064805d4f28bc9775f6cad61dce73275eb4fc8cc" } } ], "extra": [ 1, 221, 76, 250, 191, 127, 201, 88, 219, 24, 251, 225, 77, 213, 149, 233, 191, 21, 48, 189, 212, 187, 58, 146, 105, 77, 240, 170, 17, 103, 187, 110, 38, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: