Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1abdbe96046ab59f1ecadc0d210e98b6861a6fe7e8226297667b4ecd7cf619ae

Tx prefix hash: ef3e21f12c2f723e89feb1c76afe6c827e76e281991779bb97007196bba8b886
Tx public key: 373d2df9e2b73183041db744dacc4c00a1b8a6e8642e3e18100ee961fe6eecdf
Timestamp: 1578990109 Timestamp [UCT]: 2020-01-14 08:21:49 Age [y:d:h:m:s]: 05:060:05:33:13
Block: 45194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193252 RingCT/type: yes/0
Extra: 01373d2df9e2b73183041db744dacc4c00a1b8a6e8642e3e18100ee961fe6eecdf0211000000184ac5aa02000000000000000000

1 output(s) for total of 434.764782166000 dcy

stealth address amount amount idx
00: 12e89a2e4be6c56ef309660d4db230324c4e7a507f4ada700f9b3dfd9603b238 434.764782166000 82494 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": 45204, "vin": [ { "gen": { "height": 45194 } } ], "vout": [ { "amount": 434764782166, "target": { "key": "12e89a2e4be6c56ef309660d4db230324c4e7a507f4ada700f9b3dfd9603b238" } } ], "extra": [ 1, 55, 61, 45, 249, 226, 183, 49, 131, 4, 29, 183, 68, 218, 204, 76, 0, 161, 184, 166, 232, 100, 46, 62, 24, 16, 14, 233, 97, 254, 110, 236, 223, 2, 17, 0, 0, 0, 24, 74, 197, 170, 2, 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