Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aafd08880afbb1a7116f3279a46df1b8f4eadb7b33da186bdf93cd14735529cb

Tx prefix hash: 01470ca9876167fe5f69e9d50c8f555b0775fc4dd6a236b5b6c042f0c1ab244c
Tx public key: 9049e8c87c507917cb6ded973ab33a785d15dca058068e8aac77814eb8969ac2
Timestamp: 1581116825 Timestamp [UCT]: 2020-02-07 23:07:05 Age [y:d:h:m:s]: 04:325:11:10:00
Block: 60788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124158 RingCT/type: yes/0
Extra: 019049e8c87c507917cb6ded973ab33a785d15dca058068e8aac77814eb8969ac202110000001e4ac5aa02000000000000000000

1 output(s) for total of 385.997897293000 dcy

stealth address amount amount idx
00: 86083498165a9c6ee9d70e9cc03dba35e5b21b73e50ab5aec86b23f52f0fba03 385.997897293000 111959 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": 60798, "vin": [ { "gen": { "height": 60788 } } ], "vout": [ { "amount": 385997897293, "target": { "key": "86083498165a9c6ee9d70e9cc03dba35e5b21b73e50ab5aec86b23f52f0fba03" } } ], "extra": [ 1, 144, 73, 232, 200, 124, 80, 121, 23, 203, 109, 237, 151, 58, 179, 58, 120, 93, 21, 220, 160, 88, 6, 142, 138, 172, 119, 129, 78, 184, 150, 154, 194, 2, 17, 0, 0, 0, 30, 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