Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f4b096e9a2a4ec2541923b67b3748be616015d8ce109bb6037a6216dbfc4e41

Tx prefix hash: 0ed52a23859b4087591730e6b891f9820c82864acd883d9290b450ef65e6cba0
Tx public key: 41b378750a99f017b3c8460f7f478f7eef62989dd789b9cd5b941d4564e9ffd1
Timestamp: 1717062071 Timestamp [UCT]: 2024-05-30 09:41:11 Age [y:d:h:m:s]: 00:315:02:56:30
Block: 1033200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225222 RingCT/type: yes/0
Extra: 0141b378750a99f017b3c8460f7f478f7eef62989dd789b9cd5b941d4564e9ffd102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c13ff6b873270d10e2b0d2ec1fed9b94ceae79ea30bc2c90f2f8992118920c9 0.600000000000 1501663 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": 1033210, "vin": [ { "gen": { "height": 1033200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c13ff6b873270d10e2b0d2ec1fed9b94ceae79ea30bc2c90f2f8992118920c9" } } ], "extra": [ 1, 65, 179, 120, 117, 10, 153, 240, 23, 179, 200, 70, 15, 127, 71, 143, 126, 239, 98, 152, 157, 215, 137, 185, 205, 91, 148, 29, 69, 100, 233, 255, 209, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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