Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73be7e449d7a5541fe1456a26fe4ca338be5192a74b3d05019bfccdccb12257f

Tx prefix hash: f2281be7746c1df5b25bd4fcdb456d1e96b7c019583c36d50647e54e02137672
Tx public key: 44bc797c4e53c89be2ea380b5a42d441eee8c185929b98ac1aae0f34f2982023
Timestamp: 1581309010 Timestamp [UCT]: 2020-02-10 04:30:10 Age [y:d:h:m:s]: 04:332:07:43:16
Block: 61754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129695 RingCT/type: yes/0
Extra: 0144bc797c4e53c89be2ea380b5a42d441eee8c185929b98ac1aae0f34f298202302110000001d0aca7173000000000000000000

1 output(s) for total of 383.187601286000 dcy

stealth address amount amount idx
00: e0ea25670676792b7bc8eb9a4019dd6ac7af4d429f0f1ba953d48834d900062d 383.187601286000 113879 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": 61764, "vin": [ { "gen": { "height": 61754 } } ], "vout": [ { "amount": 383187601286, "target": { "key": "e0ea25670676792b7bc8eb9a4019dd6ac7af4d429f0f1ba953d48834d900062d" } } ], "extra": [ 1, 68, 188, 121, 124, 78, 83, 200, 155, 226, 234, 56, 11, 90, 66, 212, 65, 238, 232, 193, 133, 146, 155, 152, 172, 26, 174, 15, 52, 242, 152, 32, 35, 2, 17, 0, 0, 0, 29, 10, 202, 113, 115, 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