Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb976945e63646e67a8d542a35bf7dd1bed65c73b804de09712d264d9a616091

Tx prefix hash: 0ba54a8b6476407b701a48e977b45d44c9e72dce1d23133de89a13c1b3c06e5e
Tx public key: 666f26a02ef1dcceb3666975ab72ca0658b8fbd183cd7b312ab9744f30fae87b
Timestamp: 1612571178 Timestamp [UCT]: 2021-02-06 00:26:18 Age [y:d:h:m:s]: 03:335:13:03:59
Block: 192803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 998689 RingCT/type: yes/0
Extra: 01666f26a02ef1dcceb3666975ab72ca0658b8fbd183cd7b312ab9744f30fae87b021100000080aad74b3a000000000000000000

1 output(s) for total of 140.987071796000 dcy

stealth address amount amount idx
00: 3068f85f2b502d2823e877c3415b200d01d1bc8f9d0bbc842e76a7d1daf5c929 140.987071796000 389297 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": 192813, "vin": [ { "gen": { "height": 192803 } } ], "vout": [ { "amount": 140987071796, "target": { "key": "3068f85f2b502d2823e877c3415b200d01d1bc8f9d0bbc842e76a7d1daf5c929" } } ], "extra": [ 1, 102, 111, 38, 160, 46, 241, 220, 206, 179, 102, 105, 117, 171, 114, 202, 6, 88, 184, 251, 209, 131, 205, 123, 49, 42, 185, 116, 79, 48, 250, 232, 123, 2, 17, 0, 0, 0, 128, 170, 215, 75, 58, 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