Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78c841ac46d603dda32c3cebb3508d663837fac04b6d7339e3b38ce9344e87ed

Tx prefix hash: 3a83eeac2270f1aa8e3aa621b29aef08fdfe7d54253f1420f2d1260ec31a1c76
Tx public key: a176d8e67c7881c5821cdc7a8dcb65d79042df524819a689da40fc7c1fc16939
Timestamp: 1707676674 Timestamp [UCT]: 2024-02-11 18:37:54 Age [y:d:h:m:s]: 01:041:12:22:29
Block: 955387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290701 RingCT/type: yes/0
Extra: 01a176d8e67c7881c5821cdc7a8dcb65d79042df524819a689da40fc7c1fc169390211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cc769ac6450cc9f8d838851e6caf5d9c92c71f661a21c1a705802b947a73025 0.600000000000 1414675 of 15

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": 955397, "vin": [ { "gen": { "height": 955387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cc769ac6450cc9f8d838851e6caf5d9c92c71f661a21c1a705802b947a73025" } } ], "extra": [ 1, 161, 118, 216, 230, 124, 120, 129, 197, 130, 28, 220, 122, 141, 203, 101, 215, 144, 66, 223, 82, 72, 25, 166, 137, 218, 64, 252, 124, 31, 193, 105, 57, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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