Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ad81156efbec9ee35b3dd14ee8f7d2e61f8f92985be28e53a52e2c379a35f1b

Tx prefix hash: 3a44d775690280a8b3522a1ec62145062efaf26f8c58202fecf59f9c5718352d
Tx public key: 3d3722d26fe28ea49992336eb87be881f725464d86e8e5f63a88ecc9628c843f
Timestamp: 1577330172 Timestamp [UCT]: 2019-12-26 03:16:12 Age [y:d:h:m:s]: 05:310:05:26:09
Block: 31838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1369264 RingCT/type: yes/0
Extra: 013d3722d26fe28ea49992336eb87be881f725464d86e8e5f63a88ecc9628c843f0211000000044943cd9f000000000000000000

1 output(s) for total of 481.402508540000 dcy

stealth address amount amount idx
00: 88be50462e2153b5ea84d45928e4cab3d501da6ab9677439cafd48624d2f4f20 481.402508540000 52809 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 dinasty-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": 31848, "vin": [ { "gen": { "height": 31838 } } ], "vout": [ { "amount": 481402508540, "target": { "key": "88be50462e2153b5ea84d45928e4cab3d501da6ab9677439cafd48624d2f4f20" } } ], "extra": [ 1, 61, 55, 34, 210, 111, 226, 142, 164, 153, 146, 51, 110, 184, 123, 232, 129, 247, 37, 70, 77, 134, 232, 229, 246, 58, 136, 236, 201, 98, 140, 132, 63, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8