Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda213bb030c951f8bb22b354a6d65b911f302a4744c3785fcd20f726a36138b

Tx prefix hash: 5108dd28cdcfd35e33b5e899ef7575eaaab1d162b8140d03ab0a01c2f06f5e64
Tx public key: 0b83fbd41dfe39716a22f24c29a6a6aa324540e6230d0a77e70f9516817e3c91
Timestamp: 1672953833 Timestamp [UCT]: 2023-01-05 21:23:53 Age [y:d:h:m:s]: 01:331:11:14:53
Block: 668390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497908 RingCT/type: yes/0
Extra: 010b83fbd41dfe39716a22f24c29a6a6aa324540e6230d0a77e70f9516817e3c9102110000000133af99f4000000000000000000

1 output(s) for total of 3.744091276000 dcy

stealth address amount amount idx
00: ae6dc071e3840e042002513afe00fc734a8912138b98595a80409cc9287317c5 3.744091276000 1109635 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": 668400, "vin": [ { "gen": { "height": 668390 } } ], "vout": [ { "amount": 3744091276, "target": { "key": "ae6dc071e3840e042002513afe00fc734a8912138b98595a80409cc9287317c5" } } ], "extra": [ 1, 11, 131, 251, 212, 29, 254, 57, 113, 106, 34, 242, 76, 41, 166, 166, 170, 50, 69, 64, 230, 35, 13, 10, 119, 231, 15, 149, 22, 129, 126, 60, 145, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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