Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04cb322b54bc023ec8bee2634153bbc0b2f5503b088e68d90ccbe073fdc9be3b

Tx prefix hash: b104908f50b5da334e13ef485359aa5ca1ecb2afd5f0ef1d5765cbf8155fd994
Tx public key: cc8e5c9438e9e89e898db64b246b2c57d5573f59bc57e55783945a46bbe2c0cb
Timestamp: 1578380549 Timestamp [UCT]: 2020-01-07 07:02:29 Age [y:d:h:m:s]: 05:103:01:52:43
Block: 40337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1223691 RingCT/type: yes/0
Extra: 01cc8e5c9438e9e89e898db64b246b2c57d5573f59bc57e55783945a46bbe2c0cb021100000007d81c26c0000000000000000000

1 output(s) for total of 451.842595300000 dcy

stealth address amount amount idx
00: 2da25d20630b0602d4a899bb7eb3ae5fb80d0d7c98509eea4bef3f456e80e624 451.842595300000 70694 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": 40347, "vin": [ { "gen": { "height": 40337 } } ], "vout": [ { "amount": 451842595300, "target": { "key": "2da25d20630b0602d4a899bb7eb3ae5fb80d0d7c98509eea4bef3f456e80e624" } } ], "extra": [ 1, 204, 142, 92, 148, 56, 233, 232, 158, 137, 141, 182, 75, 36, 107, 44, 87, 213, 87, 63, 89, 188, 87, 229, 87, 131, 148, 90, 70, 187, 226, 192, 203, 2, 17, 0, 0, 0, 7, 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