Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc047075e8a0cadc5b3114b9bfa103eaa7b62499806707db5f1b54e6b7a1b060

Tx prefix hash: fb284040eb06d63d7309840eb856468651822b8ad513e4c163f187c8c6a24259
Tx public key: c8a366272c01c167e923e32f0bb999d1aeb9624a7e3c275acbdb976b0bea37e4
Timestamp: 1770509001 Timestamp [UTC]: 2026-02-08 00:03:21 Age [y:d:h:m:s]: 00:008:18:21:40
Block: 1472985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 6239 RingCT/type: yes/0
Extra: 01c8a366272c01c167e923e32f0bb999d1aeb9624a7e3c275acbdb976b0bea37e402081313c3b8103779be

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 593f29d3e6826ab382b066fe89f2e33580a28a0a0d10c4db9db8aa509e3bc9d2 0.000600000000 1962267 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": 1472995, "vin": [ { "gen": { "height": 1472985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "593f29d3e6826ab382b066fe89f2e33580a28a0a0d10c4db9db8aa509e3bc9d2" } } ], "extra": [ 1, 200, 163, 102, 39, 44, 1, 193, 103, 233, 35, 227, 47, 11, 185, 153, 209, 174, 185, 98, 74, 126, 60, 39, 90, 203, 219, 151, 107, 11, 234, 55, 228, 2, 8, 19, 19, 195, 184, 16, 55, 121, 190 ], "rct_signatures": { "type": 0 } }


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