Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56a47632bd046b82460f74489e984a2305ef9f3a5ac05ba35dff2a021c60ba01

Tx prefix hash: 2627da3dd2955f2cbbfb314ab4be140a914f860b5a31eecf9f6dacc5c48283f9
Tx public key: f194cbf1e9d6cd7432cb31d515a0def94483670715802509f5aee64dd09de905
Timestamp: 1724024585 Timestamp [UCT]: 2024-08-18 23:43:05 Age [y:d:h:m:s]: 00:226:03:24:40
Block: 1090929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161470 RingCT/type: yes/0
Extra: 01f194cbf1e9d6cd7432cb31d515a0def94483670715802509f5aee64dd09de90502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a64dada90977a4be897d52dd815b124d8cfd2160a9e5078c271f3040165fcf9c 0.600000000000 1565554 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": 1090939, "vin": [ { "gen": { "height": 1090929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a64dada90977a4be897d52dd815b124d8cfd2160a9e5078c271f3040165fcf9c" } } ], "extra": [ 1, 241, 148, 203, 241, 233, 214, 205, 116, 50, 203, 49, 213, 21, 160, 222, 249, 68, 131, 103, 7, 21, 128, 37, 9, 245, 174, 230, 77, 208, 157, 233, 5, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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