Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc3af222cdf6e3c6394e2c85e6eb81d2df8dca9416f2ec68a624323ffbd5a4e4

Tx prefix hash: 56101dba479a7cd8912a7d916256b7d85175d44aa0014b234984489e8e584387
Tx public key: 63f8223e39a9b0e90f538072f2f83921dac4fcc6e5238eb71be0430291baefe0
Timestamp: 1774475327 Timestamp [UTC]: 2026-03-25 21:48:47 Age [y:d:h:m:s]: 00:234:00:02:41
Block: 1505774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172655 RingCT/type: yes/0
Extra: 0163f8223e39a9b0e90f538072f2f83921dac4fcc6e5238eb71be0430291baefe0021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8772cb2a8026fe237c5ad9ce4cb0cba920086b260286ad6f6f921d9b8d8be0ea 0.000600000000 1995512 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": 1505784, "vin": [ { "gen": { "height": 1505774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8772cb2a8026fe237c5ad9ce4cb0cba920086b260286ad6f6f921d9b8d8be0ea" } } ], "extra": [ 1, 99, 248, 34, 62, 57, 169, 176, 233, 15, 83, 128, 114, 242, 248, 57, 33, 218, 196, 252, 198, 229, 35, 142, 183, 27, 224, 67, 2, 145, 186, 239, 224, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: