Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54c5d9e1d7b3784d8d30ebc8122988e44e07ff69b2cd0a88cc8ab0669d7623ff

Tx prefix hash: a91d65233d92282cac2c23a6c4bd30e265f7da7e1939728d9643e2d4ffb3108c
Tx public key: fa837a45f1e8aab09a8ca8c85c74d46f22c479e8935c6af71393ca2c434f6e0e
Timestamp: 1733014900 Timestamp [UCT]: 2024-12-01 01:01:40 Age [y:d:h:m:s]: 00:113:21:46:56
Block: 1165359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81201 RingCT/type: yes/0
Extra: 01fa837a45f1e8aab09a8ca8c85c74d46f22c479e8935c6af71393ca2c434f6e0e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab3153273c861515d4536375b11473472e5792b6429339f10cdbad4d5a9d3fe2 0.600000000000 1651034 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": 1165369, "vin": [ { "gen": { "height": 1165359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab3153273c861515d4536375b11473472e5792b6429339f10cdbad4d5a9d3fe2" } } ], "extra": [ 1, 250, 131, 122, 69, 241, 232, 170, 176, 154, 140, 168, 200, 92, 116, 212, 111, 34, 196, 121, 232, 147, 92, 106, 247, 19, 147, 202, 44, 67, 79, 110, 14, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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