Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ba7346602477d91a998217e36e7b32d95961c978343a3bb3f3b7e38dc40c5a

Tx prefix hash: 43882380c8a035761609b7293ea17a5b5bc1b7ceed72c614d762ebd2f784850e
Tx public key: 58f4bfa9ab74c335c3c51f55cc17f557e521aae9cb05bf11e13203c307b22173
Timestamp: 1578858494 Timestamp [UCT]: 2020-01-12 19:48:14 Age [y:d:h:m:s]: 05:293:15:30:47
Block: 44171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357724 RingCT/type: yes/0
Extra: 0158f4bfa9ab74c335c3c51f55cc17f557e521aae9cb05bf11e13203c307b2217302110000001fd81c26c0000000000000000000

1 output(s) for total of 438.171354666000 dcy

stealth address amount amount idx
00: 90cc7e458d283182cc2f7aa47af6de2f007510070728e7e4764cec7813f8e23b 438.171354666000 80303 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": 44181, "vin": [ { "gen": { "height": 44171 } } ], "vout": [ { "amount": 438171354666, "target": { "key": "90cc7e458d283182cc2f7aa47af6de2f007510070728e7e4764cec7813f8e23b" } } ], "extra": [ 1, 88, 244, 191, 169, 171, 116, 195, 53, 195, 197, 31, 85, 204, 23, 245, 87, 229, 33, 170, 233, 203, 5, 191, 17, 225, 50, 3, 195, 7, 178, 33, 115, 2, 17, 0, 0, 0, 31, 216, 28, 38, 192, 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