Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2bae341ee0551b01bfa8666c4f0e8d0ba6b8e24f0ebeed0e57598a83c7a2142

Tx prefix hash: 9980e3901b61ecd64844fe34eb5cfa08a0efde215651a74e5589554fed34b3c3
Tx public key: 87df2b5329b096f01c20756fb9bb377aa0678aced3edd83e3083fbc99de528f3
Timestamp: 1736101938 Timestamp [UCT]: 2025-01-05 18:32:18 Age [y:d:h:m:s]: 00:102:18:07:01
Block: 1190914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73234 RingCT/type: yes/0
Extra: 0187df2b5329b096f01c20756fb9bb377aa0678aced3edd83e3083fbc99de528f302110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68c16a2f34db8c733b2aea1114061bcdc48325082bbd91aea43783f8dd27b03b 0.600000000000 1677437 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": 1190924, "vin": [ { "gen": { "height": 1190914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68c16a2f34db8c733b2aea1114061bcdc48325082bbd91aea43783f8dd27b03b" } } ], "extra": [ 1, 135, 223, 43, 83, 41, 176, 150, 240, 28, 32, 117, 111, 185, 187, 55, 122, 160, 103, 138, 206, 211, 237, 216, 62, 48, 131, 251, 201, 157, 229, 40, 243, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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