Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7ceaa590d586e3dc29242cb135747a5c36db542b9ba62b8a0b5e1c4af80419

Tx prefix hash: 5b7f301fed3462967e04423aeefbd43545e7672597f155aedef0b31bfdb1cde8
Tx public key: 941056e0f1a8dfd38d16024e535dda65d0d83284a86d2f83e8666f2ec19d54af
Timestamp: 1581945311 Timestamp [UCT]: 2020-02-17 13:15:11 Age [y:d:h:m:s]: 05:026:06:39:39
Block: 66622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172005 RingCT/type: yes/0
Extra: 01941056e0f1a8dfd38d16024e535dda65d0d83284a86d2f83e8666f2ec19d54af021100000001026b59f3000000000000000000

1 output(s) for total of 369.193857266000 dcy

stealth address amount amount idx
00: 097ddf11c281a96f753a1fd9aefe5e6def0bd47814b70c7ea7fcd8a538e29f4d 369.193857266000 122755 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": 66632, "vin": [ { "gen": { "height": 66622 } } ], "vout": [ { "amount": 369193857266, "target": { "key": "097ddf11c281a96f753a1fd9aefe5e6def0bd47814b70c7ea7fcd8a538e29f4d" } } ], "extra": [ 1, 148, 16, 86, 224, 241, 168, 223, 211, 141, 22, 2, 78, 83, 93, 218, 101, 208, 216, 50, 132, 168, 109, 47, 131, 232, 102, 111, 46, 193, 157, 84, 175, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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