Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b6d057e7f663965919babdb7140faee21117421343655b918ddaffa21d6cf35

Tx prefix hash: 544e3029b20263a8932e30f95754fc04e026a723ab7c45ae7538dc9c8652eebe
Tx public key: 17b4f58abfcf41e9b311987c7afe903397d9df8078a0a6a9f1ecc9a3c8d0ee7f
Timestamp: 1577411443 Timestamp [UCT]: 2019-12-27 01:50:43 Age [y:d:h:m:s]: 04:336:09:57:03
Block: 32556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129543 RingCT/type: yes/0
Extra: 0117b4f58abfcf41e9b311987c7afe903397d9df8078a0a6a9f1ecc9a3c8d0ee7f02110000000d4ac5aa02000000000000000000

1 output(s) for total of 478.772630854000 dcy

stealth address amount amount idx
00: fe7ee6d24aa9377bb3ff9a60d6c982fd980f74b1250020f15a8fe5803d8ab0c5 478.772630854000 54185 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": 32566, "vin": [ { "gen": { "height": 32556 } } ], "vout": [ { "amount": 478772630854, "target": { "key": "fe7ee6d24aa9377bb3ff9a60d6c982fd980f74b1250020f15a8fe5803d8ab0c5" } } ], "extra": [ 1, 23, 180, 245, 138, 191, 207, 65, 233, 179, 17, 152, 124, 122, 254, 144, 51, 151, 217, 223, 128, 120, 160, 166, 169, 241, 236, 201, 163, 200, 208, 238, 127, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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