Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 217eaf5749f4eae950bbf7dabbd388fb91bf407228f690295bcb5fb7e2d35fa1

Tx prefix hash: e34dd3ae350d930c78cfe1d4cc37fd19bfffa478c68c44e47dbe8b228b5440f9
Tx public key: 388946da28e8c525fe64d6e3290f71f54cddbd116a1c5fd7555ade250ab4adc5
Timestamp: 1730999247 Timestamp [UCT]: 2024-11-07 17:07:27 Age [y:d:h:m:s]: 01:002:02:31:13
Block: 1148662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259921 RingCT/type: yes/0
Extra: 01388946da28e8c525fe64d6e3290f71f54cddbd116a1c5fd7555ade250ab4adc50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ef29e84eb0eaa92a2f1c0849d17a0d97601c6f1aa0eb60e9fee377887690505 0.600000000000 1633563 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": 1148672, "vin": [ { "gen": { "height": 1148662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ef29e84eb0eaa92a2f1c0849d17a0d97601c6f1aa0eb60e9fee377887690505" } } ], "extra": [ 1, 56, 137, 70, 218, 40, 232, 197, 37, 254, 100, 214, 227, 41, 15, 113, 245, 76, 221, 189, 17, 106, 28, 95, 215, 85, 90, 222, 37, 10, 180, 173, 197, 2, 17, 0, 0, 0, 2, 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