Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 316281788aac1129cf9729e7d08523fbd746204cb4d97fe2ec00b81a95c69e40

Tx prefix hash: 467f0f8662e85082b3c97606745df0eee923f5907be79c34309c218cb0abb51f
Tx public key: 227fb50fd58d62ae91d37fadc73e411db1840d9b586ba2f4acb964ba8b1321c3
Timestamp: 1771296674 Timestamp [UTC]: 2026-02-17 02:51:14 Age [y:d:h:m:s]: 00:273:09:03:00
Block: 1479470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200890 RingCT/type: yes/0
Extra: 01227fb50fd58d62ae91d37fadc73e411db1840d9b586ba2f4acb964ba8b1321c3021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7b87620adb629232f08bb8891290341f7def6ce34de3f876cf11c2a9ce34a42a 0.000600000000 1968818 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": 1479480, "vin": [ { "gen": { "height": 1479470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b87620adb629232f08bb8891290341f7def6ce34de3f876cf11c2a9ce34a42a" } } ], "extra": [ 1, 34, 127, 181, 15, 213, 141, 98, 174, 145, 211, 127, 173, 199, 62, 65, 29, 177, 132, 13, 155, 88, 107, 162, 244, 172, 185, 100, 186, 139, 19, 33, 195, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: