Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f2c770f76a1d3884bbd866034cfd966e4b3b2f7129936a2bf1fbdcb3994a30d

Tx prefix hash: 5a67c2ffbab85de3b2ac28958bd15411ba0300ccb03fa09d8d5a1a02f6e7c92e
Tx public key: 62428a89fff79464bc14a7e4207c0c74980be50f5faff2c945b98e818eb2cd5e
Timestamp: 1728196652 Timestamp [UCT]: 2024-10-06 06:37:32 Age [y:d:h:m:s]: 00:183:00:03:30
Block: 1125517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130574 RingCT/type: yes/0
Extra: 0162428a89fff79464bc14a7e4207c0c74980be50f5faff2c945b98e818eb2cd5e02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bd4a60b69f2fa62c39779799eb46567169ff5d381797b30b5f36adcbc5f2cf4 0.600000000000 1608268 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": 1125527, "vin": [ { "gen": { "height": 1125517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bd4a60b69f2fa62c39779799eb46567169ff5d381797b30b5f36adcbc5f2cf4" } } ], "extra": [ 1, 98, 66, 138, 137, 255, 247, 148, 100, 188, 20, 167, 228, 32, 124, 12, 116, 152, 11, 229, 15, 95, 175, 242, 201, 69, 185, 142, 129, 142, 178, 205, 94, 2, 17, 0, 0, 0, 10, 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