Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de894e5814efc064f15bfdd9bb5e42e5930ebd5a7d39c37889de59f6a9f65b13

Tx prefix hash: 1cf4d84bdcf10501dd51562d018946b5cff91e9ad3990cac2b3ae1ccdfcd7006
Tx public key: be9e34bfb993e9660eea891d46690533d6650783930bc69f4fb78c54ed8d287c
Timestamp: 1715706236 Timestamp [UCT]: 2024-05-14 17:03:56 Age [y:d:h:m:s]: 01:221:08:17:46
Block: 1021953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416873 RingCT/type: yes/0
Extra: 01be9e34bfb993e9660eea891d46690533d6650783930bc69f4fb78c54ed8d287c021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78baf35c64cd3f267481161576a8f87665fd1933346ab279cc8eafd231b7d062 0.600000000000 1486418 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": 1021963, "vin": [ { "gen": { "height": 1021953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78baf35c64cd3f267481161576a8f87665fd1933346ab279cc8eafd231b7d062" } } ], "extra": [ 1, 190, 158, 52, 191, 185, 147, 233, 102, 14, 234, 137, 29, 70, 105, 5, 51, 214, 101, 7, 131, 147, 11, 198, 159, 79, 183, 140, 84, 237, 141, 40, 124, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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