Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ca29e5300649a60e3df2c7f3c1be68f42a8e8529c9ad090e2ca5cd7194be5db

Tx prefix hash: eece3157d4bcf80fb9152aab44fb0537153c1609bffb8a4fc906d35ec88dbf56
Tx public key: 9b2a9d6baa4e8d26fbf3b6f99eb319e84efde1398bb69acd78c6680d69e98a2a
Timestamp: 1731511994 Timestamp [UTC]: 2024-11-13 15:33:14 Age [y:d:h:m:s]: 01:177:23:09:39
Block: 1152907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378246 RingCT/type: yes/0
Extra: 019b2a9d6baa4e8d26fbf3b6f99eb319e84efde1398bb69acd78c6680d69e98a2a021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 75e91284a843e614af187c6f4bb7e060d36fd9d68e70cf25f9ec8461aeeab7ba 0.000600000000 1638514 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": 1152917, "vin": [ { "gen": { "height": 1152907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75e91284a843e614af187c6f4bb7e060d36fd9d68e70cf25f9ec8461aeeab7ba" } } ], "extra": [ 1, 155, 42, 157, 107, 170, 78, 141, 38, 251, 243, 182, 249, 158, 179, 25, 232, 78, 253, 225, 57, 139, 182, 154, 205, 120, 198, 104, 13, 105, 233, 138, 42, 2, 17, 0, 0, 0, 1, 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: