Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3563fe6c08e2a9cd9063f42884000d281b32ff75d049b072afbb3e220e3bd4

Tx prefix hash: 3678f647457400bd1140cf0a50d77e9f6535df1a2aebc45cb566c9238dc4d93f
Tx public key: c86d2cdb3727b5bad1a183b3941df87a19df5b4574644553da388d4be1998e35
Timestamp: 1639138340 Timestamp [UCT]: 2021-12-10 12:12:20 Age [y:d:h:m:s]: 03:095:03:54:00
Block: 392479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 846754 RingCT/type: yes/0
Extra: 01c86d2cdb3727b5bad1a183b3941df87a19df5b4574644553da388d4be1998e350211000000211cab2639000000000000000000

1 output(s) for total of 30.729430358000 dcy

stealth address amount amount idx
00: 9578f82a1dea04d93d156bcfcf66af1f932711fe735f7d2a9a6110c728eb08a4 30.729430358000 789364 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": 392489, "vin": [ { "gen": { "height": 392479 } } ], "vout": [ { "amount": 30729430358, "target": { "key": "9578f82a1dea04d93d156bcfcf66af1f932711fe735f7d2a9a6110c728eb08a4" } } ], "extra": [ 1, 200, 109, 44, 219, 55, 39, 181, 186, 209, 161, 131, 179, 148, 29, 248, 122, 25, 223, 91, 69, 116, 100, 69, 83, 218, 56, 141, 75, 225, 153, 142, 53, 2, 17, 0, 0, 0, 33, 28, 171, 38, 57, 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