Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4afb8d6970b6b9839f96a3424898e67a10ecc282e69e338b4db16a43038ab91

Tx prefix hash: 7b23fd8d58eca11fdc5d55fc93d8c817cef4e16de4babd8fbcc9e5f812b264a0
Tx public key: 2e547a69c57058f5fc5fa27a6415a34f1b7bf8de09b61ba5d21da6c9e8c4a2fb
Timestamp: 1576643317 Timestamp [UCT]: 2019-12-18 04:28:37 Age [y:d:h:m:s]: 05:013:15:42:25
Block: 28151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157791 RingCT/type: yes/0
Extra: 012e547a69c57058f5fc5fa27a6415a34f1b7bf8de09b61ba5d21da6c9e8c4a2fb021100000015ad433a0b000000000000000000

1 output(s) for total of 495.136469833000 dcy

stealth address amount amount idx
00: 983eab7f62cec80e279ad351192051fca421d710789d0821f76ad42370448aee 495.136469833000 46681 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": 28161, "vin": [ { "gen": { "height": 28151 } } ], "vout": [ { "amount": 495136469833, "target": { "key": "983eab7f62cec80e279ad351192051fca421d710789d0821f76ad42370448aee" } } ], "extra": [ 1, 46, 84, 122, 105, 197, 112, 88, 245, 252, 95, 162, 122, 100, 21, 163, 79, 27, 123, 248, 222, 9, 182, 27, 165, 210, 29, 166, 201, 232, 196, 162, 251, 2, 17, 0, 0, 0, 21, 173, 67, 58, 11, 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