Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac7a4b7861b0dc8908f4db4e612047e59521e183841754c58c87112bcfd94009

Tx prefix hash: 9e3f1922f6436f9e9796fdf577c847de0deece5af0c8268aa8ae956da2afc5c5
Tx public key: 0948080fd2ef7de08cd85e890bc51091e8e3723390b9eab2feceff210585efd6
Timestamp: 1683704998 Timestamp [UCT]: 2023-05-10 07:49:58 Age [y:d:h:m:s]: 01:358:08:11:17
Block: 756900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517355 RingCT/type: yes/0
Extra: 010948080fd2ef7de08cd85e890bc51091e8e3723390b9eab2feceff210585efd602110000000275e3f0e9000000000000000000

1 output(s) for total of 1.905795464000 dcy

stealth address amount amount idx
00: 4bf861d5d7c990f2ccc50009d513050603cb90a9817c905d9aec2cf5393164d8 1.905795464000 1205297 of 0

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": 756910, "vin": [ { "gen": { "height": 756900 } } ], "vout": [ { "amount": 1905795464, "target": { "key": "4bf861d5d7c990f2ccc50009d513050603cb90a9817c905d9aec2cf5393164d8" } } ], "extra": [ 1, 9, 72, 8, 15, 210, 239, 125, 224, 140, 216, 94, 137, 11, 197, 16, 145, 232, 227, 114, 51, 144, 185, 234, 178, 254, 206, 255, 33, 5, 133, 239, 214, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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