Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fd72b07eeddf21a9626a101b53edc46a9df36f6bda54e62eb723769437f2f31

Tx prefix hash: a7bc1cd58ac144749ba9ef0bda4a1cd594f9666a0ec3ec0317ee53cb3a2ae545
Tx public key: 46f40a1172b091e004f9e51725cbbbcd0e047c8f9b4364761fed3de8b17da84b
Timestamp: 1710197240 Timestamp [UCT]: 2024-03-11 22:47:20 Age [y:d:h:m:s]: 01:020:13:43:38
Block: 976296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275672 RingCT/type: yes/0
Extra: 0146f40a1172b091e004f9e51725cbbbcd0e047c8f9b4364761fed3de8b17da84b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e37366618d375251e24807317aea429aaac87873cd2e7787e4d79f2d27317af 0.600000000000 1436287 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": 976306, "vin": [ { "gen": { "height": 976296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e37366618d375251e24807317aea429aaac87873cd2e7787e4d79f2d27317af" } } ], "extra": [ 1, 70, 244, 10, 17, 114, 176, 145, 224, 4, 249, 229, 23, 37, 203, 187, 205, 14, 4, 124, 143, 155, 67, 100, 118, 31, 237, 61, 232, 177, 125, 168, 75, 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