Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d1d8fc3469680d977b5317cc1bef0d0ab806bfc6d7136f7d826200c1a61550

Tx prefix hash: 9b9c0c373766b1afbd4800e223ec019422e4506df1c0d167e9adbc1d16371953
Tx public key: efe07cd93f08b7f492c50d7807ecf15013a4946554b1b2f3e720c962fcf9eb2b
Timestamp: 1698622627 Timestamp [UCT]: 2023-10-29 23:37:07 Age [y:d:h:m:s]: 01:164:07:56:46
Block: 880542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378447 RingCT/type: yes/0
Extra: 01efe07cd93f08b7f492c50d7807ecf15013a4946554b1b2f3e720c962fcf9eb2b021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.741991338000 dcy

stealth address amount amount idx
00: 0a809649c4fbc8a6a902478fae3f8c0121f97f3d68f65b78d5888024c7c1784c 0.741991338000 1336100 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": 880552, "vin": [ { "gen": { "height": 880542 } } ], "vout": [ { "amount": 741991338, "target": { "key": "0a809649c4fbc8a6a902478fae3f8c0121f97f3d68f65b78d5888024c7c1784c" } } ], "extra": [ 1, 239, 224, 124, 217, 63, 8, 183, 244, 146, 197, 13, 120, 7, 236, 241, 80, 19, 164, 148, 101, 84, 177, 178, 243, 231, 32, 201, 98, 252, 249, 235, 43, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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