Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ce885b429c66880a3638f38d4392c3502b2c8d447b1b20e09ad29fa83bcfee9

Tx prefix hash: 5b4b22cdf9cf2c711cc675c06602806a2f79141967ef55ca85b8bf5539cf790d
Tx public key: aa09c3d2d289672ff853a0dd30e3e38b2fd42170b0746cf29efcba2f30801c70
Timestamp: 1738642524 Timestamp [UTC]: 2025-02-04 04:15:24 Age [y:d:h:m:s]: 01:287:08:30:50
Block: 1211673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469464 RingCT/type: yes/0
Extra: 01aa09c3d2d289672ff853a0dd30e3e38b2fd42170b0746cf29efcba2f30801c70021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df7f74e11a15934c5432ac704db8d0b237dc1cd20219fb7607dfae4b1156ea77 0.000600000000 1698436 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": 1211683, "vin": [ { "gen": { "height": 1211673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df7f74e11a15934c5432ac704db8d0b237dc1cd20219fb7607dfae4b1156ea77" } } ], "extra": [ 1, 170, 9, 195, 210, 210, 137, 103, 47, 248, 83, 160, 221, 48, 227, 227, 139, 47, 212, 33, 112, 176, 116, 108, 242, 158, 252, 186, 47, 48, 128, 28, 112, 2, 17, 0, 0, 0, 3, 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: