Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30d583fc95bc0a8863f824d0cd2484cb852cab16072cdae590237a18a681e181

Tx prefix hash: fd6d928a17b05429d077ed3a11cd6d69d016fcb64b2f3b9fc0d1d41e46744577
Tx public key: 5cbd376dc17b9af44a654fcaef3bda9736d5a6ff9143d6d5433a7f941b3e53ee
Timestamp: 1770772312 Timestamp [UTC]: 2026-02-11 01:11:52 Age [y:d:h:m:s]: 00:000:14:32:23
Block: 1475162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 431 RingCT/type: yes/0
Extra: 015cbd376dc17b9af44a654fcaef3bda9736d5a6ff9143d6d5433a7f941b3e53ee02085b5dee8c59c9238c

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd5449ff79224bec3a1bec6ee28c25b2bad7d66512f2cadb5efe596692fab8ab 0.000600000000 1964462 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": 1475172, "vin": [ { "gen": { "height": 1475162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd5449ff79224bec3a1bec6ee28c25b2bad7d66512f2cadb5efe596692fab8ab" } } ], "extra": [ 1, 92, 189, 55, 109, 193, 123, 154, 244, 74, 101, 79, 202, 239, 59, 218, 151, 54, 213, 166, 255, 145, 67, 214, 213, 67, 58, 127, 148, 27, 62, 83, 238, 2, 8, 91, 93, 238, 140, 89, 201, 35, 140 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369