Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeacf04ca76958d60a75e78b27b02dd0b7f49f73344595bb4a934ad504094dfb

Tx prefix hash: eb077f3c5b15fe96f145e50631186a4bdf01f2e907c58aa6869a4fca5113af6f
Tx public key: 1cf6cc6528fab0a9f6863511cf18ec8004d81a84fbfbd0655c4626cc263a3c33
Timestamp: 1578952021 Timestamp [UCT]: 2020-01-13 21:47:01 Age [y:d:h:m:s]: 05:003:16:00:49
Block: 44982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152938 RingCT/type: yes/0
Extra: 011cf6cc6528fab0a9f6863511cf18ec8004d81a84fbfbd0655c4626cc263a3c3302110000000f4943cd9f000000000000000000

1 output(s) for total of 435.468556166000 dcy

stealth address amount amount idx
00: 9d51984f27882b46839c138d55682db647e379eb3ec58b73252b16014f741ba1 435.468556166000 82028 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": 44992, "vin": [ { "gen": { "height": 44982 } } ], "vout": [ { "amount": 435468556166, "target": { "key": "9d51984f27882b46839c138d55682db647e379eb3ec58b73252b16014f741ba1" } } ], "extra": [ 1, 28, 246, 204, 101, 40, 250, 176, 169, 246, 134, 53, 17, 207, 24, 236, 128, 4, 216, 26, 132, 251, 251, 208, 101, 92, 70, 38, 204, 38, 58, 60, 51, 2, 17, 0, 0, 0, 15, 73, 67, 205, 159, 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