Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7951eed89cf8ec2ee82e6f8c7098889105caa49a8005f1a437e0b39f2667a722

Tx prefix hash: bd2d3c480ca4557eaa2bf6b0db2253cdf6cbe7ffa9c8810acaaf622aafa54630
Tx public key: 776f24da2df4d9a6e0c3a37c493ff4bfe3fb0d3174c7cef4f072529c4edf671b
Timestamp: 1770551188 Timestamp [UTC]: 2026-02-08 11:46:28 Age [y:d:h:m:s]: 00:008:20:44:53
Block: 1473334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 6306 RingCT/type: yes/0
Extra: 01776f24da2df4d9a6e0c3a37c493ff4bfe3fb0d3174c7cef4f072529c4edf671b0208b821e0c1ee43d49e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3944361d811c99c08e94d36027d5071675d293e877302a19faca11c5305e7a45 0.000600000000 1962616 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": 1473344, "vin": [ { "gen": { "height": 1473334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3944361d811c99c08e94d36027d5071675d293e877302a19faca11c5305e7a45" } } ], "extra": [ 1, 119, 111, 36, 218, 45, 244, 217, 166, 224, 195, 163, 124, 73, 63, 244, 191, 227, 251, 13, 49, 116, 199, 206, 244, 240, 114, 82, 156, 78, 223, 103, 27, 2, 8, 184, 33, 224, 193, 238, 67, 212, 158 ], "rct_signatures": { "type": 0 } }


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