Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f867ec1f813db3786902cb076315a43ac0f07c5388a4d05ca2e8e2b15daa60

Tx prefix hash: 5d759fb8916b375a80c81a234cffa0893dbc9cde17b55f0f64f113b71d72eb72
Tx public key: 8a067c9c83944804f17d088ff93fea698a5b5b3b1846a0a6c61a9e25e743c987
Timestamp: 1724111338 Timestamp [UCT]: 2024-08-19 23:48:58 Age [y:d:h:m:s]: 00:230:03:35:58
Block: 1091646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164338 RingCT/type: yes/0
Extra: 018a067c9c83944804f17d088ff93fea698a5b5b3b1846a0a6c61a9e25e743c98702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00dd413eb0aa91b8d6d42d7dfbb176cd9b459ad844d291689ea01b08d8d3382a 0.600000000000 1566279 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": 1091656, "vin": [ { "gen": { "height": 1091646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00dd413eb0aa91b8d6d42d7dfbb176cd9b459ad844d291689ea01b08d8d3382a" } } ], "extra": [ 1, 138, 6, 124, 156, 131, 148, 72, 4, 241, 125, 8, 143, 249, 63, 234, 105, 138, 91, 91, 59, 24, 70, 160, 166, 198, 26, 158, 37, 231, 67, 201, 135, 2, 17, 0, 0, 0, 1, 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