Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bbc240ae22063aefd569d0975f85834e9c1352d02693bdcf0f1e00deee0b674

Tx prefix hash: c989a04ed8251879fe86830aa6edc6ce5841ea41966e32d29e34bade2aba5dd0
Tx public key: 8bb31e1e453df3d1fcb12fff2748766bb422c949ab52391e93ca0f4f492ba3f4
Timestamp: 1745401867 Timestamp [UTC]: 2025-04-23 09:51:07 Age [y:d:h:m:s]: 01:017:06:17:20
Block: 1267630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263564 RingCT/type: yes/0
Extra: 018bb31e1e453df3d1fcb12fff2748766bb422c949ab52391e93ca0f4f492ba3f4021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6a7eae1c67175021f36b491761aec9eb6ffd9bd7c383e3dd8c351c301fcaecc0 0.000600000000 1754859 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": 1267640, "vin": [ { "gen": { "height": 1267630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a7eae1c67175021f36b491761aec9eb6ffd9bd7c383e3dd8c351c301fcaecc0" } } ], "extra": [ 1, 139, 179, 30, 30, 69, 61, 243, 209, 252, 177, 47, 255, 39, 72, 118, 107, 180, 34, 201, 73, 171, 82, 57, 30, 147, 202, 15, 79, 73, 43, 163, 244, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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: