Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b880ab77ef564d150c602f5e45e03978f7a07a07129bd77b17ef3fa9aba76f0e

Tx prefix hash: f79ca2806c74d30974a8714b69a3d18790191e79f44b0c0133ed231a9c301aeb
Tx public key: 910c83630d1f32df977206b4e4013b3e4ee08a5d83796a6d034c516d097fb156
Timestamp: 1714024292 Timestamp [UCT]: 2024-04-25 05:51:32 Age [y:d:h:m:s]: 00:306:00:32:48
Block: 1008002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218742 RingCT/type: yes/0
Extra: 01910c83630d1f32df977206b4e4013b3e4ee08a5d83796a6d034c516d097fb15602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10136ff341561dcde3337cfd4be1ced8ae163446e9ecbef00a2e17730cc5f85f 0.600000000000 1469468 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": 1008012, "vin": [ { "gen": { "height": 1008002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10136ff341561dcde3337cfd4be1ced8ae163446e9ecbef00a2e17730cc5f85f" } } ], "extra": [ 1, 145, 12, 131, 99, 13, 31, 50, 223, 151, 114, 6, 180, 228, 1, 59, 62, 78, 224, 138, 93, 131, 121, 106, 109, 3, 76, 81, 109, 9, 127, 177, 86, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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