Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 256235a9b2797b4017c8a9ff98da22ee7f56db3ad95e250ea7ca887b186e9168

Tx prefix hash: 70e935b1dce052548364c9192f1bbbbf52e83a9d52a69afe912b50e2c44ce8ec
Tx public key: cce43da5074ebd2c9529250c4b190630fd5401d3b02a4231c532606d81078c3a
Timestamp: 1576284084 Timestamp [UTC]: 2019-12-14 00:41:24 Age [y:d:h:m:s]: 06:067:12:19:52
Block: 26951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1452824 RingCT/type: yes/0
Extra: 01cce43da5074ebd2c9529250c4b190630fd5401d3b02a4231c532606d81078c3a02110000004a9159db1e000000000000000000

1 output(s) for total of 0.499690411457 xmr

stealth address amount amount idx tag
00: cd86c81fda9c9d231eeba31565762686ccb186ba86fd79701f9e011045fc8b97 0.499690411457 44451 of 0 -

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": 26961, "vin": [ { "gen": { "height": 26951 } } ], "vout": [ { "amount": 499690411457, "target": { "key": "cd86c81fda9c9d231eeba31565762686ccb186ba86fd79701f9e011045fc8b97" } } ], "extra": [ 1, 204, 228, 61, 165, 7, 78, 189, 44, 149, 41, 37, 12, 75, 25, 6, 48, 253, 84, 1, 211, 176, 42, 66, 49, 197, 50, 96, 109, 129, 7, 140, 58, 2, 17, 0, 0, 0, 74, 145, 89, 219, 30, 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) | dinastycoin version: tesla-369