Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f29ebb821f4968db3a528e2fb20c7625222a4e8870624dbf72fa739d65d2a7

Tx prefix hash: 38430eb1501213cabf303705aa48480ae452cc45efbe962e4a2e6062b9b005b6
Tx public key: 7bc884a41817f4a59af03aa8275b079bc33ca8f363af4d2c29a7ae40a854d494
Timestamp: 1711611603 Timestamp [UCT]: 2024-03-28 07:40:03 Age [y:d:h:m:s]: 00:288:10:53:20
Block: 988019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206472 RingCT/type: yes/0
Extra: 017bc884a41817f4a59af03aa8275b079bc33ca8f363af4d2c29a7ae40a854d49402110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42491069d7eda47a9de15a4cb8094022ca5df6ce0e373ad9eb027bb12b1f0f60 0.600000000000 1448280 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": 988029, "vin": [ { "gen": { "height": 988019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42491069d7eda47a9de15a4cb8094022ca5df6ce0e373ad9eb027bb12b1f0f60" } } ], "extra": [ 1, 123, 200, 132, 164, 24, 23, 244, 165, 154, 240, 58, 168, 39, 91, 7, 155, 195, 60, 168, 243, 99, 175, 77, 44, 41, 167, 174, 64, 168, 84, 212, 148, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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