Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250d9cfd1b8c5f4e35af7ad30e4e1019afef43f1db22e6cdafc02ea2bf912cf7

Tx prefix hash: 821c252458cce769dfc3b118a1921bba421de00bf59e7f402df13408f891bb8c
Tx public key: 57ff7668515a1cff36f053a8dda317100e243edfffcb8b02233d14da67f2e3b6
Timestamp: 1705842165 Timestamp [UCT]: 2024-01-21 13:02:45 Age [y:d:h:m:s]: 01:086:10:13:17
Block: 940144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322879 RingCT/type: yes/0
Extra: 0157ff7668515a1cff36f053a8dda317100e243edfffcb8b02233d14da67f2e3b60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6c372d52e2074ced2d8d15ed54cdb5d86e168068d3183270d376a85319b463e 0.600000000000 1398278 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": 940154, "vin": [ { "gen": { "height": 940144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6c372d52e2074ced2d8d15ed54cdb5d86e168068d3183270d376a85319b463e" } } ], "extra": [ 1, 87, 255, 118, 104, 81, 90, 28, 255, 54, 240, 83, 168, 221, 163, 23, 16, 14, 36, 62, 223, 255, 203, 139, 2, 35, 61, 20, 218, 103, 242, 227, 182, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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