Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5026322df573947c2b916b778811e10ffbf71d06b5da57d0068566981205e3

Tx prefix hash: 66937f959c86e65880eab3c9b9540740f33ce0fd012f34291e60f1339667c6cb
Tx public key: 4a0a5dff1903639b2187294eb4660eea19b83e9098d429fea40d899164a645f2
Timestamp: 1581824690 Timestamp [UCT]: 2020-02-16 03:44:50 Age [y:d:h:m:s]: 05:018:17:30:44
Block: 66066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1166151 RingCT/type: yes/0
Extra: 014a0a5dff1903639b2187294eb4660eea19b83e9098d429fea40d899164a645f20211000000037adf42d3000000000000000000

1 output(s) for total of 370.763289051000 dcy

stealth address amount amount idx
00: e2cf3d31f4502ff53cb9aa4b4d089f85a6cd3c23ee8594611ddc872cc61259ce 370.763289051000 121715 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": 66076, "vin": [ { "gen": { "height": 66066 } } ], "vout": [ { "amount": 370763289051, "target": { "key": "e2cf3d31f4502ff53cb9aa4b4d089f85a6cd3c23ee8594611ddc872cc61259ce" } } ], "extra": [ 1, 74, 10, 93, 255, 25, 3, 99, 155, 33, 135, 41, 78, 180, 102, 14, 234, 25, 184, 62, 144, 152, 212, 41, 254, 164, 13, 137, 145, 100, 166, 69, 242, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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